Skip to main content

Documentation Index

Fetch the complete documentation index at: https://jetemail.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
Introduction

You will see this response when JetEmail blocks a specific sender (an SMTP user or an address) after detecting one of:
  • Spam content being submitted through the smarthost
  • Abuse signals (high complaint rate, suspicious patterns, list-bombing, etc.)
  • Sustained rate-limit breaches that go beyond a normal throttle
The block is targeted at the offending sender, not your whole account.

​
Example error message

user@example.com
   host relay.jetsmtp.net [103.173.0.0]
   SMTP error from remote mail server after end of data:
   550 5.7.1 [ABUSE] Sender blocked: spam or abuse detected.
   See: https://reports.jetsmtp.net/?id=1ec5d310c951ebd54d84&auth=33fb6ec0-5aa9-4b3f-b312-4d7189471226
The report URL in the error explains exactly why the block was applied (spam content, abuse signals, or rate-limit breaches) and lists the matching evidence. Open it first; it is the fastest path to understanding the block.

​
What does this mean?

JetEmail’s outbound protections continuously evaluate every send across three axes:
  1. Spam content: message scoring, suspicious links, header/body shape, etc. (see also 550 [SPAM])
  2. Abuse signals: complaint rate, recipient-list quality, list-bombing patterns, deliberate evasion attempts
  3. Rate: sustained sending well beyond the normal limits for your plan or smarthost (see also 421 4.7.1 Rate limit)
If the combined signal is strong enough we block the offending sender to protect the wider sending reputation of the platform. Other SMTP users on your account continue to send normally.

​
How to fix this error

  1. Open the report URL in the bounce. It identifies the specific reason (spam, abuse, or rate) and the evidence behind it.
  2. Stop the offending traffic. Pause whatever campaign or process triggered the block before retrying. Continued sends will extend or escalate the block.
  3. Fix the underlying problem. Depending on what the report flagged:
    • Spam content: edit subject, body, links, or headers per the report’s signals. See 550 [SPAM].
    • Abuse: review how the recipient list was collected, remove unknown or scraped addresses, and add or fix a working unsubscribe path.
    • Rate: slow your send rate, batch sends across a longer window, or upgrade your plan if you need sustained higher throughput.
  4. Request a review from the report page if you believe the block was applied incorrectly.

​
Reducing future abuse blocks

  • Only send to recipients who clearly opted in.
  • Keep a working List-Unsubscribe header on all bulk mail and honour unsubscribes immediately.
  • Monitor complaint and bounce rates and pause campaigns that drift out of bounds.
  • Throttle programmatic sends so a single bug cannot empty an entire queue into the relay in seconds.
  • Use a separate SMTP user per app or product so a problem in one workflow is isolated.

​
Getting help

Click Report message on the report URL to send the case straight to our team with all the evidence already attached. You can also reach out to JetEmail Support if the block needs manual review by our compliance team.